Network element connection management within a network management system

ABSTRACT

Preferred embodiments of the invention provide systems and methods to receive a logical command, the logical command being associated with a target identifier of a network element, determine connection parameters of the network element based on the target identifier, define a work flow based on the logical command, the work flow including a connection manager work unit, and execute the connection manager work unit to retrieve a connection from a connection pool based on the connection parameters.

CROSS-REFERENCE TO RELATED APPLICATIONS

This present patent application is a divisional of U.S. patent application Ser. No. 11/615,276, filed Dec. 22, 2006, entitled “NETWORK ELEMENT CONNECTION MANAGEMENT WITHIN A NETWORK MANAGEMENT SYSTEM.” The disclosure of this priority application is hereby incorporated by reference herein in its entirety.

BACKGROUND INFORMATION

Direct network element connection does not implement a connection pool in an efficient manner. Also, without a connection pool, a network management system cannot implement management strategies to maximize connection efficiency.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to facilitate a fuller understanding of the exemplary embodiments of the disclosure, reference is now made to the appended drawings. These drawings should not be construed as limiting, but are intended to be exemplary only.

FIG. 1 illustrates an exemplary implementation of a system according to an embodiment of the disclosure.

FIG. 2 illustrates an exemplary implementation of a network management system according to an embodiment of the disclosure.

FIG. 3 illustrates an exemplary implementation of a web portal according to an embodiment of the disclosure.

FIG. 4 illustrates an exemplary screen diagram of a web portal according to an embodiment of the disclosure.

FIG. 5 illustrates an exemplary implementation of a web services portal according to an embodiment of the disclosure.

FIG. 6 illustrates an exemplary screen diagram of an operations module according to an embodiment of the disclosure.

FIG. 7 illustrates an exemplary implementation of a connection pool module according to an embodiment of the disclosure.

FIG. 8 illustrates an exemplary implementation of a method for implementing a connection pool within a network management system according to an embodiment of the disclosure.

FIG. 9 illustrates an exemplary implementation of a method for evicting an idle connection according to an embodiment of the disclosure.

FIG. 10 illustrates an exemplary implementation of a method for sharing a connection according to an embodiment of the disclosure.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

A system and process of an exemplary embodiment of the disclosure provides an implementation of a connection pool within a network management system.

FIG. 1 is an exemplary network system according to an embodiment of the disclosure. System 100 illustrates an exemplary system for supporting telecommunication networks, such as packet-switched based networks and/or circuit-switched based networks. As illustrated, one or more interfaces 103 a-103 n may be coupled to network management system 102 and network management system 102 may be coupled to network 101. The various components of system 100 may be further duplicated, combined and/or integrated to support various applications and platforms. Additional elements may also be implemented in the system to support various applications. Also, while one configuration is shown in FIG. 1, other configurations of these various units may also be implemented. For example, the various components of system 100 may be components within network 101 and network 101 may include one, or any number of the exemplary types of networks operating as a stand alone network or in cooperation with each other.

In various exemplary embodiments, network 101 may comprise one or more packet-switched based networks and/or circuit-switched based networks. As such, network 101 may include, for example, one or more Internet Protocol (IP) networks, wireless communication networks, and/or access networks including, without limitation, dial-up networks, digital subscriber line (DSL) networks, broadband wireless access networks, cable modem networks, integrated services digital networks (ISDN), symmetric high-speed digital subscriber line (SHDSL) networks, Ethernet networks, metro Ethernet networks, gigabit Ethernet networks, frame relay networks, asynchronous transfer mode (ATM) networks, synchronous optical networking (SONET) networks operating as a stand alone network or in cooperation with each other.

Network 101 may be associated with an entity and may provide network connectivity to its users (e.g., customers) For example, network 101 may be associated with a network access provider such as an Internet service provider (ISP) and or any other network access provider that may provide network connectivity to enable users (e.g., customers) of the network to transmit information via network 101; a global network provider such as an Internet backbone provider that may provide Internet backbone connection facilities around the world; a telephone network provider that may be part of a public switch telephone network; and/or a wireless communication network provider that may provide wireless broadband and/or mobile phone services to its users (e.g., customers).

Network 101 may be comprised of one or more network elements 104 a-104 n. In various exemplary embodiments, network elements 104 a-104 n may represent, for example, addressable, manageable hardware device(s) and associated software that may perform a telecommunication service function. Network elements 104 a-104 n may include, without limitation: devices associated with level one of the Open Systems Interconnection (OSI) reference model such as add/drop multiplexers, optical add/drop multiplexers, and/or like devices; devices associated with level two of the Open Systems Interconnection (OSI) reference model such as an asynchronous transfer mode (ATM) switch and/or any other like device; devices associated with level three of the Open Systems Interconnection (OSI) reference model such as routers, switches, and or any other like devices; and/or any other computer networking device that may transmit data across a network. In various exemplary embodiments, network elements 104 a-104 n may also represent, for example, automated telephone exchanges, digital switches, and/or other like devices associated with the public switch telephone network (PSTN).

The entity or entities associated with network 101 may manage network 101 via network management system 102. As illustrated in FIG. 1, network management system 102 may be coupled to network 101 and interfaces 103 a-103 n. In various exemplary embodiments, network management system 102 may provide a scalable network management application, for example, to manage devices (e.g., network elements 104 a-104 n) on network 101. Network management system 102 may also provide a web-based interface across Open Systems Interconnection (OSI) layers for network elements 104 a-104 n. Network management system 102 may also be coupled to other systems 105 and provide seamless integration with other systems 105. Other systems may include, for example, provisioning systems, operational support systems (OSS), and fault, configuration, accounting, performance, and security (FCAPS) systems.

Network management system 102 may support various functions associated with the management of network 101. For example, network management system 102 may support activation needs for provisioning requests to network elements 104 a-104 n; auto-discovery, reporting, reconciliation, and restoration needs for provisioning platforms; capabilities similar to those of an enterprise management system; and the ability to view or make changes to virtual devices without accessing the network element directly as described in greater detail below. In various exemplary embodiments, network management system 102 may be associated with users that may use network management system 102 to manage network 101, for example, and administrators that may configure and/or manage the network management system. Users may also refer to automated systems associated with the network management and/or users of other systems 105 and interfaces 103 a-103 n. Also, users may be administrators and whether a user may act as an administrator may be dependent upon privileges associated with the user as described in greater detail below.

Interfaces 103 a-103 n may represent any number of interfaces associated with supporting network management tasks. In various exemplary embodiments, interfaces 103 a-103 n may be referred to as northbound interfaces. As such, interfaces 103 a-103 n may send various logical requests to network management system 102, which may then transform the logical requests into native commands to a network element, for example. In an exemplary embodiment, interfaces 103 a-103 n may be associated with provisioning systems, operational support systems (OSS), and fault, configuration, accounting, performance, and security (FCAPS) systems. Accordingly, while FIG. 1 illustrates interfaces 103 a-103 n as being separate from other systems 105, other configurations may also be implemented. For example, interfaces 103 a-103 n may be interfaces to other systems 105.

FIG. 2 illustrates a network management system 102 according to various embodiments of the disclosure. As shown in FIG. 2, network management system 102 may include web portal 201, security management system 202, workflow management system 203, connections module 204, activation module 205, and execution module 206.

FIG. 3 illustrates a web portal 201 according to various embodiments of the disclosure. As shown in FIG. 3, web portal 201 may include admin portal 301 and web services portal 302. Admin portal 301 may include security module 303, admin module 304 and reports module 305. Web portal 201 may provide a single interface to manage all activities associated with a network. For example, web portal 201 may provide a graphical user interface (GUI) that enables a single access point to all network elements within a network such that users may execute commands on a network element, add, delete, or modify network element configurations, troubleshoot and resolve network problems, and/or backup and restore deleted configurations. Web portal 201 may also provide a graphical user interface (GUI) that allows an administrator, for example, to add, delete or modify user profiles of users and/or user groups of the network management system, track all actions performed by users of the network management system, send messages to users of the network management system, run reports based on information contained within the network management system, and/or create credentials and map users that may be permitted to access a network element.

In various exemplary embodiments, web portal 201 may be organized based on tabs. FIG. 4 depicts an exemplary embodiment of a screen diagram 400 which illustrates a web portal based on tabs. Screen diagram 400 may represent a graphical user interface (GUI) as described above with respect to web portal 201. Screen diagram 400 may include a main page 401 that may provide a main entry screen from which all modules of the network management system can be accessed. As shown in FIG. 4, screen diagram 400 may also include security tab 402 a, admin tab 403 a, inventory tab 404 a, reports tab 405 a, services tab 406 a, and links tab 407 a. Each tab may enable users of the network management system to access different information and/or services associated with the respective tab. Also, each tab may be associated with different modules and/or portals of the network management system. For example, security tab 402 a may be associated with a security module, admin tab 403 a may be associated with an admin module, inventory tab 404 a may be associated with an operations portal, reports tab 405 a may be associated with a reports module, and services tab 406 a may be associated with a web services portal.

Screen diagram 400 may also include various links on main page 401 that may be associated with the respective tabs. For example, main page 401 may include a security link 402 b that may be associated with security tab 402 a, an admin link 403 b that may be associated with admin tab 403 a, an inventory link 404 b that may be associated with inventory tab 404 a, a reports link 405 b that may be associated with reports tab 405 a, and a services link 406 b that may be associated with services tab 406 a. In an exemplary embodiment, if a user of the network management system wishes to navigate to one of the modules and/or portals associated with a tab, the user may activate (e.g., click on) the tab and/or the link, for example.

Screen diagram 400 may also include other navigational tools such as a site map button 408 and navigation buttons 409, which may enable a user of the network management system to navigate through the web portal or access a help page, for example.

Referring back to FIG. 3, in various exemplary embodiments, admin portal 301 may include a security module 303 which may allow an administrator to manage users of a network management system. Users of the network management system may be assigned privileges within the network management system by way of the roles, groups, and organizations to which they are associated.

Roles, for example, may be inherited by a user based on a user's group or organization. Exemplary roles may include, without limitation, system admin, admin, user, manager, and complex services user. Each role may include tab permission levels to determine whether or not a user can modify or view data. The tab permission levels may be associated with various tabs of a web portal as shown an described with respect to FIG. 4. For example, if a role has view privileges for a tab associated with the web portal, then the user may only view the data and not modify the data associated with the tab. Similarly, if a role has modify privileges for a tab, a user may modify the data associated with the tab.

User groups and/or organizations may represent a collection of users of the network management system that may have a common purpose within an organization associated with the network. For example, one user group may represent all users who share a similar job function. Also, a user group may represent all users who have access to a particular network element and/or group of network elements. For example, one user group may represent all users who have access to the network elements associated with a particular network operation center (NOC). User groups may also represent all users within a specific geographic region.

In various exemplary embodiments, an administrator may add and/or delete users and/or modify information associated with users. For example, security module 303 may include an “add user” tab that may enable an administrator to add a user and provide information associated with a user to create a user profile. The “add user” tab may include a “user information” tab and a “user privileges” tab which may provide an interface to enter information about a user and the privileges (e.g., roles and organizations) associated with the user, respectively. Security module 304 may also include a “modify user” tab that may enable an administrator to modify the information associated with users of the network management system. To modify the information associated with a user the “modify user” tab may enable a search for the respective user provide fields of information that may be modified. Security module 304 may also enable the administrator to delete users.

Security module 303 may also include an “audit trail” tab that may enable an administrator to track security-related actions on a per-user basis and/or a “command audit” tab that may enable an administrator to track all commands on a network element. For example, via an “audit trail” tab, an administrator may identify a user and track which network elements the user accessed. Similarly, via a “command audit” tab, an administrator may identify a particular network element and track all commands and/or requests that that may have been executed or are scheduled to be executed on a network element.

Admin portal 301 may also include an admin module 304 which may enable communication between and among users of the network management system. For example, admin module 304 may enable administrators to send banner messages to users of the network management system. In various exemplary embodiments, admin module 304 may include a “message center” tab that may enable an administrator to send a message to one or more users. Using the “message center” tab, an administrator, for example, may select individual users (by selecting a specific user identifier) or a group of users (by selecting a user group) and enter a message to be sent to the selected users. Users may also be able to send messages to other users using, for example, the “message center” tab. In doing so, users may be able to send message to other users based on privileges associated with the user sending the message.

Admin portal 301 may also include a reports module 305 which may enable reports to be generated that are related to, for example, the activities of users within the network management system. For example, reports module may enable “181 Day Reports” to be generated which may display a list of users who have not accessed the network management system in 181 days. In various exemplary embodiments, reports module 306 may enable the generation of other reports that may provide information about, for example, which network elements a particular user accessed, what commands were executed on a particular network element, and/or the like.

FIG. 5 depicts an exemplary embodiment of a web services portal 302 according to various embodiments of the disclosure. As shown in FIG. 5, web services portal 302 may include a user module 501 and an admin module 502. User module 501 may include an operations module 503, an activation module 504, and a network elements module 505. Admin module 502 may include a policy module 506, a network elements module 507, and a credentials module 508.

Operations module 503 may enable users of the network management system to execute commands on a network element and/or add, modify and/or delete network element configurations. Operations module 503 may also provide secure access to network elements to enable users to troubleshoot and resolve network problems.

Operations module 503 may include an “terminal” tab that may enable users to connect to a network element and enter commands to be executed on the network element. In an exemplary embodiment of the invention, to access the network element, operations module may log on to the network element in a manner that may be transparent to the user as described in greater detail below. Also, operations module 503 may batch all commands entered during a session and then commit the commands to the network element at one time, for example.

FIG. 6 depicts an exemplary embodiment of a screen diagram 600 which illustrates an exemplary “terminal” tab according to various embodiments of the disclosure. As shown in FIG. 6, screen diagram 600 may include a “terminal” tab 601 which may be accessed by activating (e.g., clicking on) terminal tab button 610. Screen diagram 600 may also include a security tab 602 which may be similar to security tab 402 a as described above, an admin tab 603 which may be similar to admin tab 403 a as described above, an inventory tab 604 which may be similar to inventory tab 404 a as described above, a reports tab 605 which may be similar to security tab 405 a as described above, a services tab 606 which may be similar to security tab 406 a as described above, a links tab 607 which may be similar to links tab 407 a as described above, a site map button 608, navigation buttons 609, connection status portion 611, command portion 612, and response portion 613.

Using, information about a network element such as a network element identifier, protocol type, Internet protocol (IP) address and/or port number, a user may search for and locate a device (e.g., network element) that the user desires to access. In an exemplary embodiment, a user may only access network elements that the user has privileges to access based on the user's role and/or organization. Similarly, a user may only execute commands that the user has privileges to execute based on policies that may be associated with the user and/or user credentials.

Once a user has identified and/or accessed a network element, a user may interact with the network element via “terminal” tab 601. As shown in FIG. 6, connection status portion 611 may display the status of the connection between the network management system and the network element. For example, connection status portion 611 may indicate “Connection has been established with [IP Address] (Device Name) on port [Port]”, where [IP address represents an Internet protocol (IP) address of the network element, “(Device Name) represents a unique identifier of the device, and “[Port] represents the port number. Using command portion 612, a user may enter commands into command field 614. For example, a user may enter transaction language one (TL1), common object request broker architecture (CORBA), command line interface (CLI), and/or other like commands into command field 614. In various exemplary embodiments, different network elements may support different command sets. In these embodiments, the network management system may validate the different types of commands and commit the commands to the network element as described in greater detail below. Once the commands are entered, the commands may be displayed in response portion 613, for example. As noted above, operations module 503 may batch all commands entered during a session and then commit the commands to the network element at one time. Users may also activate (e.g., click on) disconnect button 615 to disconnect from a network element. Once disconnected, connection status portion 611 may indicate “Not Connected,” for example.

Referring back to FIG. 5, activation module 504 may enable users to add, modify and/or manage scripts for other systems (e.g., other systems 105) that may interface with the network management system. In various exemplary embodiments, data sent from other systems may be converted into, for example, transaction language one (TL1) commands. The scripts may represent a set of commands that an other system may apply to a network element.

In various exemplary embodiments, a script may include, without limitation, the following three components: a tree structure, a validation script, and a configuration script. The tree structure may represent the extensible markup language (XML) command structure. The validation script may include a set of commands that may verify what already exists in the network element before performing a configuration script. For example, where a configuration script is associated with a cross connect, the validation script may validate whether a cross connect exists before executing a configuration script to establish the cross connect and utilize the ports. The configuration script may add, modify, and/or delete data. For example, a configuration script may create a cross connect. Other configuration scripts may define an Internet protocol (IP) interface, create a subnet, and build a border gateway protocol (BGP) interface to a neighbor router.

Activation module 504 may include an “activation template” tab that may enable users to add modify and manage template scripts. Template scripts may be used repeatedly to perform a particular task associated with a particular network element. Activation template scripts may be associated with a particular network element and/or type of network element. Also, users may access templates based on privileges of the user. Using the “activation template” tab, users having requisite privileges may add, modify and/or delete template scripts to be executed by themselves and/or other users.

Activation module 504 may also include an “activation request” tab that may enable users to select an activation template and execute the script associated with the selected template on a network element. In various exemplary embodiments, this “activation request” tab may provide an alternate to issuing commands using, for example, the “terminal” tab as described above. Also, the “activation request” tab may enable users to schedule scripts to execute at a future date and time. When executing a script and/or template script, users may enter, for example, network element inputs and/or script input inputs that may be inserted into variable fields in the script. Users may also be able to preview the script having the inputs inserted into the variable fields before execution.

Network elements module 505 may enable users to add, delete, and/or modify network element configurations. Network elements module 505 may include an “add element” tab which may include various fields within which users may enter information about a network element. For example, the “add element” tab may include fields associated with a unique identifier, a host name of the network element, a device type to specify the model name for the network element, a device version to specify the release version of the network element, an Internet protocol (IP) address, a port number, a credential, a loop back, and or any other information associated with a network element. To add a network element, users may enter the information into the input fields and activate (e.g., click on) an add button associated with the “add element” tab.

To modify or delete a network element, users may search for the network element and once located, modify or delete the network element details, for example. A user may add, modify, and/or delete network element details based on the privileges associated with the user.

As noted above, admin module 502 may include a policy module 506. In various exemplary embodiments, a policy may refer to a set of commands that determine the commands a particular user and/or group of users may execute. Policy module 506 may enable administrators, for example, to add, delete, and/or modify a policy, and/or apply a policy to a group, role, user, or network element.

Admin module 502 may include a “manage policy” tab that may enable an administrator to manage the policies within the network management system. To create or modify a policy, an administrator may select a device from a list of devices displayed within the “manage policy” tab. Once selected, an administrator may view, for example, a list of commands that are permitted for that network element.

In various exemplary embodiments, a policy may be identified by an alphanumeric identifier. To add a policy, an administrator may locate a network element and enter an alphanumeric name into, for example a name field within the “manage policy” tab to associate the network element with the name of the policy. Each policy may have an associated default policy which may determine how the permissions will work. Exemplary default policies may include, without limitation, allow, deny, and/or abstain. Allow may represent that, by default, all commands may be allowed, except, for example, those commands that may be explicitly flagged by add, modify, delete, and/or query permission flags. Deny may represent that, by default, commands may be denied, except, for example, those commands that may be explicitly flagged by add, modify, delete, and/or query permission flags. Abstain may represent that no behavior may be defined. In an exemplary embodiment, selecting abstain may result in an implicit deny of any command.

Within the “manage policy” tab, an administrator may associate add, modify, delete, or query permissions to a command. An administrator may also apply a policy to groups, users, roles, or network elements. Doing so may define what commands may be executed by certain group(s), user(s), role(s), and on what network elements.

Admin module 502 may also include a network elements module 507 that may enable an administrator, for example, to return a network element to a state of a previous provisioning in the system. Returning a network element to a state of a previous provisioning may provide disaster recovery for a network element, for example. Network elements module 507 may include a “network element reconcile” tab that may enable an administrator to locate a network element by searching for the network element and select any number of commands from a list of commands provided with the “network element reconcile” tab and re-execute the selected commands.

Admin module 502 may also include a credentials module 508 that may enable an administrator to map users and groups to a network element. In various exemplary embodiments, each network may be associated with a network element ID and a password. As described in greater detail below, the network management system to connect to the network element in a manner that may be transparent to a user. A user may not be able to access a network element until the user is mapped to the network element.

A credential may be associated with a credential name, a network element ID, and a password of the network element. Credentials module 508 may include a “credential mapping” tab that may enable an administrator to add a credential. To add a credential, the administrator may input information into, for example, credential name, network element, and network element password fields within the “credential mapping” tab. Once added, an administrator may associate users, user groups, and/or network element groups to the credential. Once a user is associated with a network element, the user may log on to the network element via the web portal, for example.

Referring back to FIG. 2, security management system 202 may provide generic security concepts to network management system 102 and network 101. For example, security management system 202 may provide credentials control, key escrow services, firewall rules management, access and controls specification, secured auditing and/or encryption/decryption services. These exemplary generic security concepts may then be utilized as a base services offering (i.e., a business delegate), to the network management system to provide a common mechanism for repetitive security-related events such as login credentials control to network elements.

In various exemplary embodiments, security management system 202 may also provide some or all of the data structures and/or algorithms associated with performing the functions of security module 303, policy module 506, network elements module 507, and/or credentials module 508 as described above.

Workflow management system 203 may manage work flow (or work unit flow) of the network management system. As described herein, work flow (or work unit flow) may represent a collection of work units. Generally, work flow may represent any operation performed by the network management system. For example, work flow may represent operations for connecting to a network element, communicating with a network, element, and/or interfacing with other systems. Programmatically, a work unit may represent an object that executes in the work flow and returns a state information to the workflow management system.

As noted above, network elements may represent addressable, manageable hardware device(s) and associated software that may perform a telecommunication service function. Each network element may expose one or more management interfaces that the network management system may use to communicate with and/or manage the network element. The management interfaces may use a variety of protocols, depending on the type of network element. These protocols may include, without limitation, simple network management protocol (SNMP), transaction language one (TL1), command line interface (CLI), extensible markup language (XML), common object request broker architecture (CORBA) and/or hypertext transfer protocol (HTTP).

In various exemplary embodiments, network management system 102 may provide a single interface to interact with a network element, regardless of the protocol used by the network element. Workflow management system 203 may define a different work unit type for each protocol. For example, workflow management system 203 may define a simple network management protocol (SNMP) work unit type, a transaction language one (TL1) work unit type, a command line interface (CLI) work unit type, extensible markup language (XML) work unit type, a common object request broker architecture (CORBA) work unit type, a hypertext transfer protocol (HTTP) work unit type and so forth.

Workflow management system 203 may manage interactions with numerous network elements at a given time. As noted above, to manage work flow, workflow management system 203 may use the state information returned by the work unit object. Although work unit objects may be defined for each protocol, workflow management system 203 may manage work flow using state transitions that are based upon patterns. In various exemplary embodiments, patterns may represent regular expressions that match data arriving on an incoming stream. Workflow management system may monitor incoming data streams for patterns that may be represented in three exemplary ways.

First, a good pattern may provide an indication to workflow management system 203 that the one or more operations specified in a command were performed successfully and that workflow management system can transition successfully. Second, a bad pattern may indicate that the transition was completed, the prompt was found, but an error message occurred during the runtime. Such an indication may mean that the transition is to enter a failure transition, for example. Moreover, when a bad pattern is identified, the workflow management system 203 may wait for a prompt from the network element. If an error message is received from the network element, there may be an unknown amount of time before the stream may flush to get caught up so the next pattern does not false hit on stream data. Third, an error pattern may indicate that a problem is found on the stream and the state of the link with the network element may no longer be important. If an error pattern is identified, the workflow management system 203 may enter an error state transition and allow for recovery.

Using the command line interface as an exemplary protocol, as noted above, workflow management system 203 may define a command line interface (CLI) work unit type. The command line interface (CLI) work unit type may be an object-oriented data structure that may define various functions for managing work flow. For example, the command line interface (CLI) work unit type may define a main execution function may send a command to a network element and wait for response patterns to be received from the network element. The command line interface (CLI) work unit may also define a command that may be sent to a stream and associated “get” and “set” functions to get and set the command, respectively. In an exemplary embodiment, the “get function may return a string value that is associated with the command.

The command line interface (CLI) work unit may also define good, bad and/or error patterns and associated functions for “adding” good, bad, and/or error patterns. Within the definition of the command line interface (CLI) work unit, a good pattern may indicate to the command line interface (CLI) work unit the pattern(s), when found, that may force the work flow into a good transition state. In an exemplary embodiment, a good pattern may indicate that the prompt was found and no error was generated by the network element. An error pattern may indicate to the command line interface (CLI) work unit the pattern(s), when found, that may force the work flow into a bad transition state. In an exemplary embodiment, an error pattern may indicate that a prompt was found at the same time an error pattern was found. For example, the network element may return the prompt with a percentage sign (%) to indicate that an error occurred. In this instance, when a prompt is returned with an error indication (%), the stream returned may the be scrubbed by workflow management system 203 to determine the error pattern. Scrubbing the stream in this manner may enable workflow management system 203 to understand the stream and make future transitions possible. A bad pattern may indicate that total recovery should occur. For example, the state of the stream may contain an error that requires connection invalidation, recovery, re-login and/or back-out. A bad pattern may be identified by workflow management system 203 by directly examining the stream before the prompt is returned.

Other protocol work unit types may be defined and workflow management system 203 may manage work flow using state transitions that are based upon patterns associated with the respective work unit types.

Connections module 204 provide and manage connections between network management system 102 and remote facilities such as, e.g., network elements and/or other systems. As noted above, network management system 102 may connect to various network elements using a number of different protocols and ports. Connections module 204 may define a model for which all connections may adhere to and provide a common mechanism for interfacing with a connection pool manager, for example. In an exemplary embodiment, the model and mechanism may be defined as an object-oriented classes or like data structure.

The common model, as defined in connections module 204 may define one or more methods for enabling connections to remote facilities. For example, connections module 204 may define a method to create a connection and/or handle to a remote facility and initiate credentials by executing the login workflow. In an exemplary embodiment, the creation of a connection may be executed as part of the work flow and managed by workflow management system 203. Connections module 204 may also define a method to close resources in use by a connection and remove a connection to a remote facility.

In various exemplary embodiments, depending on the protocol associated with a connection, connections module 204 may define a method to flush any data from a connection so that operations may start over.

Connections module 204 may also define a method that may validate the stability of a connection and return true if the connection id valid, or false otherwise. The implementation of this method may vary based on the protocol that is associated with a connection. Also, in an exemplary embodiment, method may provide an indication that a communication vehicle is valid, but not an indication of a logged in state.

Connections module 204 may also define methods to set the state of the connection, set and/or return the workflow utilized to keep the connection alive during idle periods, validate that a connection is in a “logged in” stat and that the connection is properly open, return a cache utilized in a connection, override a default cache created during object creation, store a connection pool manager, return a connection pool manager for a session, set a session identification for a current session, and/or return a stored session identification for the current session. In various exemplary embodiments, the session identification may be utilized by a connection pool manager to identify a connection.

As noted above, connections module 204 may provide a common mechanism for interfacing with a connection pool manager. Accordingly, connections module 204 may define a session manager to manage a connection pool. In various exemplary embodiments, the session manager may be defined as an object-oriented class and/or data structure. The session manager may define a function to “get” a connection. In an exemplary embodiment, given a session parameter, the function to “get” a connection may return a new connection from a pool or as a newly created connection. In such an embodiment, the session parameters may provide session specific data to generate the connection and/or pull a connection from a pool. The session manager may also define a “return” connection function that may return the connection back to a pool so that the connection may be returned back to a connection pool to be used by another thread that may require access to a remote facility. The session manager may define another connection that may “remove” a connection that may be determined to be totally invalid. In an exemplary embodiment, a connection that is “removed” may be completely closed so that it may not be reused.

Activation module 205 may provide a mechanism to implement an activation interface as described above with respect to activation module 504.

Execution module 206 may provide an interface that enables users of network management system to interact with network elements and/or other remote facilities (e.g., other systems 105). As such execution module 206 may enable execution of commands to a network element or other device. To do so, execution module 206 may provide a mechanism to receive one or more commands to be executed and pass the commands to an interface associated with the device on which the commands are to be executed, get a connection from a connection pool, process the list of commands based on the interface associated with the device on which the commands are to be executed, load the commands into work flow units, insert the connection into the work flow, and/or execute the work flow. In various exemplary embodiments, execution module 206 may execute commands based on a priority associated with the user and/or a priority associated with the command. For example, a user may be a high-priority user (e.g., an operations support user) and network troubleshooting commands executed by that user may be given a high priority. A user may also be a low-priority user (e.g., a provisioning system user) and provisioning commands executed by that user may be given a lower priority. In various exemplary embodiments, the priority of a user may be assigned dynamically.

In various exemplary embodiments, the network management system may establish and maintain numerous connections between a plurality of users of the network management system and the plurality of network elements within the network. For example, a first user may connect to a first network element through the network management system in an attempt to commit one or more commands to the first network element. At approximately the same time and/or while the first user is idle, a second user may connect to a second network element through the network management system in an attempt to commit one or more commands to the second network element. A network management system (e.g., network management system 102) may include a connection pool manager that may establish a connection to the network element and maintain, for example, a “virtual session” between the users using the network management system and the network elements the users are “connected to.” In various exemplary embodiments, the connection pool manager may be implemented within a connections module (e.g., connections module 204) of a network management system.

A connection pool manager according to various exemplary embodiments of the disclosure may also implement management strategies to maximize connection efficiency. For example, a connection pool manager may implement management strategies to reduce connection times, reduce network element resource usage, and/or overall network management efficiency.

A connection pool may refer to a plurality of network element connections maintained by the network management system so that connection may be reused when the network management system attempts to connect to network elements. A connection may refer to an association established between functional units for conveying information, an association established by a given layer in the Open Systems Interconnection architecture between two or more entities of the next higher layer for purpose of data transfer, and/or the path between two protocol applications that provides reliable data stream delivery service (e.g., a connection that may extend from a transmission control protocol (TCP) application on one system to a Transmission Control Protocol (TCP) application on another system). Also, a session may refer to all of the activities which take place during the establishment, maintenance, and/or release of a connection for purposes of data communication, a logical connection between elements that can be activated, tailored to provide various protocols, and deactivated.

FIG. 7 depicts an implementation of a connection pool module 700 according to an exemplary embodiment of the disclosure. In a network management system as described above, connection pool module 700 may be implemented within a connections module (e.g., connections module 204). As shown in FIG. 7, connection pool module 700 may include, for example, a parameters module 701, a session module 702, and a session manager module 703. Each of the modules associated with connection pool module 700 as well as connection pool module 700 may represent one or more data objects, data structures, and or object-oriented classes.

Parameters module 701 may define an object or like data structure that all session parameters for a corresponding connector type may utilize when passing creation entities, for example. As noted above, a network management system may interact with network elements that may use a variety of different protocols (e.g., simple network management protocol (SNMP), transaction language one (TL1), command line interface (CLF), extensive markup language (XML), common object request broker architecture (CORBA), and/or hypertext transfer protocol (HTTP). A network management system according to exemplary embodiments of the disclosure may define a connector type to be associated with each of the different protocols of the network elements. For example, the network management system may define a command line interface (CLI) connector type that may be utilized when communicating with network elements that use the command line interface (CLI) protocol. These connector types may be defined and/or stored within a connections module 204, and/or a connections pool module 700 and/or a parameters module 701.

In an exemplary embodiment where parameters module 701 defines a data object, the data object represented by parameters module 701 may be a base class in which all parameters for the corresponding connector type may utilize when creating session creation entities. In such an embodiment, the base class may be abstract in that the child class may implement the required value, but the base class may be utilized when passing data to, for example, session module 702, so that functions implemented within session module 702 may execute unilaterally.

Session module 702 may define a data object or like data structure for all connectors. In an exemplary embodiment, a connector may represent the pathway or connection to a network element. The data object defined by session module 702 may be a base class for all connectors. In such an embodiment, this base class may define a model which all higher level connections may adhere to and provide a common class to be passed around to items such as the connection pool in a polymorphic manner.

Session module 702 may define one or more methods to provide the common class as described above. These methods may include, without limitation, an open method, a close method, a flush method, a check connection method, a set method, a validation method, a set work flow method, a get work flow method, a get cache method, a get cache method, a set connection manager method, a get connection manager method, a set session identifier method, and/or a get session identifier method.

The open method may create a connection and/or handle to a network element and initiate credentials by executing a login workflow, for example. In an exemplary embodiment, the open method may be an abstract method that may be implemented in a child class that may implement the logic of a specific protocol type.

The close method may close any resources in use by a connection and break down the connection to a network element. The close method may also be an abstract method that may be implemented in a child class that may implement the logic of a specific technology type.

The flush method may flush any data from a connection so that operations may start anew. The flush method may be implemented in a child class that implements the logic of a specific technology type. Also, the flush method may not be relevant to all connection technology types. Where the flush method is not relevant, the flush method may return success in the base class.

The check connection method may validate the stability of a connection and return true if the connection is still valid or false otherwise. In an exemplary embodiment, the check connection method may be an abstract method that may be implemented in a child class that implements the logic of a specific technology type. The implementation details of the check connection method may be specific to the connection methodology, for example. Also, the check connection may or may not indicate that a connection is in a “logged-in” state, however, the check connection method may indicate that the underlying communication vehicle is still valid.

The set method may enable a child class to set the state of a connection.

The validation method may validate that a connection is in a “logged-in” or “user-begin” state and that the connection is properly open. In an exemplary embodiment, a “logged-in” or “user-begin” state may refer to any state prior to activating a network element.

The set workflow method may set a workflow that may be utilized to keep a connection alive during idle periods. The specific implementation of the set workflow method may be connection and/or instance specific. The get workflow method may return the workflow utilized to keep during idle periods.

The get cache method may return a cache utilized in a connection. In an exemplary embodiment, a cache may be set aside to store “cached” facilities of a connection. For example, using TMF814 as an example, the cache may store top level objects which may be utilized repeatedly to reduce latency from looking up the same object repeatedly. The set cache method may permit an override of the default cache created during object creation.

The set connection manager method may store the connection pool.

The get connection manager method may return the connection pool manager.

The set session identifier method may set a session identifier for a current session. In an exemplary embodiment, the set session identifier may be used by a connection pool manager to identify the connection. Also, the set session identifier method may override a default session identifier that may be created during object initialization.

The get session identifier method may return a session identifier that may be stored in a current instance.

In various exemplary embodiments, other methods may be defined by session module 702 to provide a base class for all connectors.

Session manager module 703 may manage a connection pool. Session manager module 703 may pull a proper connection based upon the details that generate the key for which connection it requires. These details may be stored and/or defined in parameters module 701, for example. Session manager module 703 may also define one or more methods to manage the connection pool. For example, session manager module 703 may define a get connection method, a return connection method, and/or a remove connection method.

The get connection method may return a new connection give a session parameter. The new connection may be returned from the connection pool and/or be a newly created connection. The session parameters may provide session specific data to generate a connection and/or pull a connection from the pool knowing the connection contains the connection required. In an exemplary embodiment, the logic for the get connection method may be encapsulated in a workflow.

The return connection method may return a connection back to the connection pool so that the connection may be used by another thread that may access the network elements.

The remove connection method may remove a connection from the connection pool so that the connection may not be reused and/or the connection may be completely closed. In an exemplary embodiment, a connection may be removed if a connection is invalid.

As noted above, a connection pool may be implemented within a network management system as shown and described above. FIG. 8 depicts flow diagram 800 which illustrates an exemplary method for implementing a connection pool manager within network management system.

In block 801, a logical command may be received by a network management system. The logical command may represent a command to a network element in a network associated with the network management system. The network element may be represented by a target identifier within the network management system. The target identifier for all network elements within the network may be maintained by the network management system in a database associated with the network management system. This database may also store other information about each network element and the target identifier may serve as a key into the database.

In block 802, connection parameters associated with the network element may be determined. For example, using the target identifier as a key, the network element may lookup connection parameters in a database that stores information about each network element. Connection parameters may include, without limitation, credentials, user identification, password, Internet protocol (IP) port, device name, connection pool name, and any other information about the network element.

In block 803, the connection parameters may be set into the work flow context. In various exemplary embodiments, the work flow context may define critical information associated with the work flow. For example, the critical information may include a definition of the network element based on the connection parameters.

In block 804, the work flow may be defined. The work flow may be defined using work units and may contain a plurality of work units to be used in executing the command(s) on the network element. One of the work units may include a connection manager work unit and the connection manager work unit may be the first work unit to execute when the work flow begins to execute. The connection manager work unit may maintain the connection to the network element during execution of the work flow.

In block 805, the work flow may begin executing. An execution module (e.g., execution module 206) may begin to execute the work units. As noted above, the first work unit to execute may be the connection manager work unit. The connection manager work unit may determine its state in block 806. The state of the connection manager work unit may be represented by three values—unassigned, initialized, and failed. Unassigned may indicate that the connection manager is executing for the first time and may need to obtain a connection from the connection pool. Initialized may represents that a valid connection exists to the network element. Failed may represent a connection failure and may require invalidation and/or removal of the connection before a connection may be reestablished with the network element.

In block 807, a method may be invoked to get a connection from the connection pool. Using, for example, the connection parameters, this method may determine the connection pool name and use the connection pool name as a key to lookup an object associated with the connection pool.

In block 808, a method may be invoked to build a network connection and/or define a path to an idle connection. Using, for example, the connection parameters, build a network connection and/or define a path to an idle connection.

In block 809, the work flow may be executed using the connection from the connection pool. To execute the work flow, an execution module may execute the work units contained in the work flow. For example, the execution module may execute work units associated with commands to the network element.

In block 810, attempts may be made to reestablish the connection to the network element. For example, to reestablish a connection, a current connection may be invalidated and a new connection may be obtained from the connection pool.

In block 811, an error may be generated if a connection to the network element fails and cannot be reestablished.

A connection pool module as shown and described may implement one or more management strategies to maximize connection efficiencies. To implement these management strategies, one or more methods may be defined within the modules of the connection pool module. For example the connection pool module may define the connection pool depending on the type of network element, geographic location of the network element, utilization of network elements, stability of the network and/or one or more network elements, and/or anything else that may be associated with the load and/or capabilities of a network element. Doing so may enable the network management system to contain multiple pools to accommodate different requirement of the network management system, northbound interfaces, and/or other systems.

Also, the connection pool module may support multiple connection pool configurations. Supporting multiple connection pool configurations. Supporting multiple connection pool configurations may enable multiple connection pools to be defined within a single connection pool.

The connection pool module may also share multiple sessions per physical connection. As noted above, a session may refer to all of the activities which take place during the establishment, maintenance, and/or release of a connection for purposes of data communication, a logical connection between elements that can be activated, tailored to provide various protocols, and deactivated. Also, a connection may refer to an association established between functional units for conveying information, an association established by a given layer in the Open Systems Interconnection architecture between two or more entities of the next higher layer for purpose of data transfer, and/or the path between two protocol applications that provides reliable data stream delivery service. In an exemplary embodiment, the connection pool module may interleave sessions through a physical connection to support multiple sessions per physical connection. For example, using the transaction language one (TL1) protocol as an example, the connection pool module may interleave ctags to provide multiple sessions per physical connection.

The connection pool module may also support keyed pooling of the connection pool at the physical address associate with a network elements, a port associated with the network element, a target identifier associated with the network element and/or user credentials. The target identifier associated with the network element may be maintained by the network management system and represent a logical identifier of the network element. Also, by pooling a connection based on user credentials, the connection pool module may eliminate overhead from logon execution because only one login may be required per connection.

In various exemplary embodiments, the connection pool module may support eviction of idle connections. FIG. 9 depicts flow diagram 900, which illustrates an exemplary method for evicting an idle connection. In block 901, a connection may be kept alive. As noted above, a connection pool module may define a method (e.g., a set workflow method) to set a work flow to keep a connection alive during idle periods.

In block 902, the connection may be tested. To test the connection, the connection pool module may define a method (e.g., check connection method and/or validate method) to test the connection. The get workflow method may return the workflow used to keep the connection alive.

In block 903, the connection pool module may determine whether to evict the connection. For various exemplary embodiments, a connection may be evicted because the connection has been idle for too long, a user associated with the connection is a lower-priority user, and/or all physical connections associated with a network element are exhausted. In block 904, the connection may be evicted. To evict a connection, the connection module may define and implement a method to remove the connection (e.g., remove method as described above. The remove method may also log a user out during eviction.

In block 905, the connection may be maintained. In an exemplary embodiment, the connection may be maintained using, for example, the set workflow method as discussed above.

The connection pool module may also support the sharing of an idle connection. In various exemplary embodiments, network elements may permit multiple sessions and the network management system may establish multiple “virtual connections” that may resolve to one physical connection of the network element. To do so, the connection pool may serve as a multiplexer and demultiplexer of “virtual connections” to a network element by enabling sharing of an idle connection, for example. FIG. 10 depicts flow diagram 1000 which illustrates an exemplary method for sharing a connection with blocks 1001-1002 operating as described for blocks 901-902.

In block 1003, the connection pool may determine whether to share a connection. In various exemplary embodiments, a connection may be shared because the physical connections to a network element are exhausted and/or an idle connection cannot be found. To determine whether to share a connection, the connection pool module examine the physical connections to a network and make a determination that a connection is not available.

In block 1004, to share a connection, the connection pool module may use an idle connection that is associated with another user. For example, using the transaction one language protocol (TL1), the connection pool module can interleave multiple sessions through a single physical connection.

In block 1005, the connection may be maintained as is, using, for example, the set workflow method as described above.

In the preceding specification, various preferred embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded in an illustrative rather than restrictive sense. 

1. A method, comprising: maintaining a connection to a network element; testing the connection to determine a status of the connection; determining whether to evict the connection based on the status of the connection; and evicting the connection based on a determination to evict the connection.
 2. The method according to claim 1, wherein the connection is an idle connection.
 3. The method according to claim 1, wherein the status of the connection indicates that the connection has been idle for a period of time that exceeds an acceptable period of time.
 4. The method according to claim 1, wherein the status of the connection indicates that the connection is associated with a low-priority user.
 5. The method according to claim 1, wherein the status of the connection indicates that physical connections to the network elements are exhausted.
 6. A method, comprising: maintaining a connection to a network element; testing the connection to determine a status of the connection; determining whether to share the connection based on the status of the connection; and sharing the connection based on a determination to share the connection.
 7. The method according to claim 6, wherein the sharing the connection comprises interleaving multiple sessions on a physical connection.
 8. The method according to claim 6, wherein the status of the connection indicates that an idle connection is unavailable.
 9. The method according to claim 6, wherein the status of the connection indicates that physical connections to the network elements are exhausted.
 10. The method according to claim 6, wherein the determining comprises examining physical connection associated with the network.
 11. A non-transitory computer readable medium comprising code which when executed causes a computer to perform a method comprising: maintaining a connection to a network element; testing the connection to determine a status of the connection; determining whether to evict the connection based on the status of the connection; and evicting the connection based on a determination to evict the connection.
 12. The method according to claim 11, wherein the connection is an idle connection.
 13. The method according to claim 11, wherein the status of the connection indicates that the connection has been idle for a period of time that exceeds an acceptable period of time.
 14. The method according to claim 11, wherein the status of the connection indicates that the connection is associated with a low-priority user.
 15. The method according to claim 11, wherein the status of the connection indicates that physical connections to the network elements are exhausted.
 16. A non-transitory computer readable medium comprising code which when executed causes a computer to perform a method comprising: maintaining a connection to a network element; testing the connection to determine a status of the connection; determining whether to share the connection based on the status of the connection; and sharing the connection based on a determination to share the connection.
 17. The method according to claim 16, wherein the sharing the connection comprises interleaving multiple sessions on a physical connection.
 18. The method according to claim 16, wherein the status of the connection indicates that an idle connection is unavailable.
 19. The method according to claim 16, wherein the status of the connection indicates that physical connections to the network elements are exhausted.
 20. The method according to claim 16, wherein the determining comprises examining physical connection associated with the network. 